System for Accessing and Browsing A PLC Provided Within A Network

ABSTRACT

Certain exemplary embodiments can comprise a method, comprising: recognizing, by a PLC, that a memory device has been connected to the PLC; and configuring the PLC via a PLC executable software program resident on the memory device. Certain exemplary embodiments can comprise a method, comprising: via a PLC network interface: presenting a PLC network as a namespace shell extension of an operating system of a non-PLC information device; and rendering, to a user of the non-PLC information device, the PLC network as a node of a network. Certain exemplary embodiments can comprise a method, comprising: via a PLC network interface: presenting a PLC network as a namespace shell extension of an operating system of a non-PLC information device; and searching the PLC network for at least one item corresponding to one or more search parameters.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. patent application Ser. No. 11/143,836(Attorney Docket No. 2005P09442US), filed Jun. 2, 2005, which claimspriority to, and incorporates by reference herein in their entireties,the following U.S. Provisional patent applications:

-   -   Application No. 60/577,804 (Attorney Docket No. 2004P09695US),        filed Jun. 8, 2004;    -   Application No. 60/577,943 (Attorney Docket No. 2004P09696US),        filed Jun. 8, 2004; and    -   Application No. 60/577,823 (Attorney Docket No. 2004P09697US),        filed Jun. 8, 2004.

BACKGROUND

PLC configurations are frequently stored on a CPU, rather than thedevice that is being configured. As a result, when a device is moved, itcan be necessary to reconfigure the device on the new CPU. This can be atimely, costly process and/or specialized expertise may be needed whenreconfiguring the device for use on the new CPU. Thus, portable PLCconfigurations that enable efficient movement of devices with theircorresponding configuration between PLCs can be desirable. When a PLCdevice is moved between PLC systems, or moved within the same PLCsystem, reconfiguration can be necessary in order for the device tooperate in the same manner as before.

Documentation for a PLC control process can be vital for operation andmaintenance of the PLC system. In order to accurately and safelymaintain a PLC-based control system, a great deal of information can berequired that is independent from the actual operating PLC program.

Many forms of documentation might exist that can aid in the operationand maintenance of a PLC-based control system. These might include PLCcontrol project source files, engineering documentation, wiringdiagrams, CAD drawings, etc. However, conventional PLC systems do nottypically have the ability to store these files. As a result, the filescan be unavailable for maintenance, for portability to up-gradedsystems, and/or to expand an existing or new PLC system. Accordingly,documentation often must be separately provided for each PLC of aconventional PLC network by maintenance and/or engineering personnel.This conventional system and method of file management of documentationon a PLC can be timely and/or costly.

In conventional systems, it can be necessary to develop specializedsoftware to connect and communicate with a PLC network. Specializeddialogs and/or windows might need to be created to view informationabout attached PLCs and the information provided can be very limited.Often, it is not possible to utilize standard filed management andbrowser systems such as Explorer by Microsoft.

Therefore, it can be desirable to enable easeful and fast browsing of aPLC network and/or to provide significant, helpful information abouteach PLC as a user is browsing the PLC network. Also, it can bedesirable to quickly determine the contents of a PLC network and/or thestatus of the various PLCs attached in a network.

SUMMARY

Certain exemplary embodiments can comprise systems, interfaces,machine-readable mediums, and/or methods for automatically:

-   -   configuring a PLC based on an executable software program        resident on a memory device coupled to the PLC;    -   presenting, to a user of a non-PLC information device, a PLC        network as network node and/or a PLC (and/or a memory device        coupled to a PLC, etc.), as a component of a network node;    -   enabling a user of a non-PLC information device to browse a PLC        network, a PLC, and/or a memory device coupled to a PLC, etc.;        and/or    -   enabling a user of a non-PLC information device to search a PLC        network, PLC, and/or a memory device coupled to a PLC, etc., for        at least one item corresponding to one or more search        parameters.

BRIEF DESCRIPTION OF THE DRAWINGS

A wide variety of potential embodiments will be more readily understoodthrough the following detailed description of certain exemplaryembodiments, with reference to the accompanying exemplary drawings inwhich:

FIG. 1 is a block diagram of an exemplary embodiment of a system 1000;

FIG. 2 is a flowchart of an exemplary embodiment of a method 2000;

FIG. 3 is a flowchart of an exemplary embodiment of a method 3000;

FIG. 4 is a flowchart of an exemplary embodiment of a method 4000;

FIG. 5 is a block diagram of an exemplary embodiment of an informationdevice 5000; and

FIGS. 6 through 35 are screen shots of exemplary embodiments of theS7-200 Explorer.

DEFINITIONS

When the following terms are used substantively herein, the accompanyingdefinitions apply:

-   -   a—at least one.    -   access—to approach, enter, exit, communicate with, and/or make        use of.    -   activity—an action, act, step, and/or process or portion        thereof.    -   adapted to—made suitable or fit for a specific use or situation.    -   address—a code that identifies where a piece of information is        stored and/or where a node is located.    -   allow—to permit and/or let happen.    -   animation—humanly visible and varying graphics.    -   apparatus—an appliance or device for a particular purpose    -   audio—humanly audible and varying sounds.    -   automatically—acting or operating in a manner essentially        independent of external influence or control. For example, an        automatic light switch can turn on upon “seeing” a person in its        view, without the person manually operating the light switch.    -   block item—a logically-separate data package, such as, for        example, a program block, user block, and/or system block, etc.    -   browse—to look around casually, randomly, and/or purposefully.    -   can—is capable of, in at least some embodiments.    -   command—a signal that initiates an operation defined by an        instruction.    -   communication parameter—a variable related to communicating via        a network.    -   comprising—including but not limited to.    -   configure—to design, arrange, set up, and/or shape for a        specific purpose.    -   connected—physically and/or logically linked.    -   content—the subject matter of a written work and/or electronic        file.    -   data—distinct pieces of information, usually formatted in a        special or predetermined way and/or organized to express        concepts.    -   data block—a portion of a memory dedicated to storing one or        more sets of data.    -   data log—a record of data events.    -   define—to establish the outline, form, or structure of.    -   determine—ascertain, obtain, and/or calculate.    -   EEPROM (Electrically Erasable Programmable Read-Only Memory)—a        non-volatile storage device using a technique similar to the        floating gates in EPROMs but with the capability to discharge        the floating gate electrically.    -   electronic file—a collection of related data or program records        stored in a memory as a unit with a single name.    -   Ethernet—a frame-based computer networking technology for local        area networks (LANs). It defines wiring and signaling for the        physical layer, and frame formats and protocols for the media        access control (MAC)/data link layer of the OSI model.    -   executable—able to run.    -   execute—run.    -   file creation—a date on which an electronic file was generated.    -   file name—a computer-readable and/or user readable identifier        for an electronic file.    -   file type—an indicator of an application program used to create        and/or open an electronic file.    -   firmware—a program that is stored in non-volatile memory built        from integrated circuits.    -   folder—a collection of computer files; a directory of computer        files; an icon in a graphic user interface that represents a        collection of items, such as computer files.    -   graphical—a pictorial representation.    -   hierarchical structure—a visible classification scheme that        accords with various criteria, the scheme having successive        levels or layers.    -   highlight—to identify, illuminate, and/or draw attention to.    -   icon—in a graphical user interface (GUI), a pictorial, on-screen        representation of an object, such as a file, program, folder, or        disk drive.    -   identify—to name; to establish the identity and/or existence of.    -   image—a representation of a photograph and/or other picture.    -   information device—any device capable of processing information,        such as any general purpose and/or special purpose computer,        such as a personal computer, workstation, server, minicomputer,        mainframe, supercomputer, computer terminal, laptop, wearable        computer, and/or Personal Digital Assistant (PDA), mobile        terminal, Bluetooth device, communicator, “smart” phone (such as        a Treo-like device), messaging service (e.g., Blackberry)        receiver, pager, facsimile, cellular telephone, a traditional        telephone, telephonic device, a programmed microprocessor or        microcontroller and/or peripheral integrated circuit elements,        an ASIC or other integrated circuit, a hardware electronic logic        circuit such as a discrete element circuit, and/or a        programmable logic device such as a PLD, PLA, FPGA, or PAL, or        the like, etc. In general any device on which resides a finite        state machine capable of implementing at least a portion of a        method, structure, and/or or graphical user interface described        herein may be used as an information device. An information        device can comprise well-known components such as one or more        network interfaces, one or more processors, one or more memories        containing instructions, and/or one or more input/output (I/O)        devices, one or more user interfaces coupled to an I/O device,        etc.    -   input/output (I/O) device—any sensory-oriented input and/or        output device, such as an audio, visual, haptic, olfactory,        and/or taste-oriented device, including, for example, a monitor,        display, projector, overhead display, keyboard, keypad, mouse,        trackball, joystick, gamepad, wheel, touchpad, touch panel,        pointing device, microphone, speaker, video camera, camera,        scanner, printer, haptic device, vibrator, tactile simulator,        and/or tactile pad, potentially including a port to which an I/O        device can be attached or connected.    -   instance—an occurrence of something, such as an actual usage of        an individual object of a certain class. Each instance of a        class can have different values for its instance variables,        i.e., its state.    -   instructions—directions adapted to perform a particular        operation or function.    -   item—a computer file, folder, volume, disk, and/or node.    -   machine readable medium—a physical structure from which a        machine can obtain data and/or information. Examples include a        memory, punch cards, etc.    -   manage—to direct or control the use of; handle.    -   may—is allowed to, in at least some embodiments.    -   memory device—an apparatus capable of storing analog or digital        information, such as instructions and/or data. Examples include        a non-volatile memory, volatile memory, Random Access Memory,        RAM, Read Only Memory, ROM, flash memory, magnetic media, a hard        disk, a floppy disk, a magnetic tape, an optical media, an        optical disk, a compact disk, a CD, a digital versatile disk, a        DVD, and/or a raid array, etc. The memory device can be coupled        to a processor and/or can store instructions adapted to be        executed by processor, such as according to an embodiment        disclosed herein.    -   method—a process, procedure, and/or collection of related        activities for accomplishing something.    -   modification—a change to a content of an electronic file.    -   namespace shell extension—a mechanism for adding customized        functionality to an operating system in such a manner that the        custom functionality appears to the user to be a substantially        seamless part of the operating system.    -   network—a communicatively coupled plurality of nodes.    -   network interface—any device, system, subsystem, and/or software        capable of coupling an information device to a network. For        example, a network interface can be a telephone, cellular phone,        cellular modem, telephone data modem, fax modem, wireless        transceiver, Ethernet card, cable modem, digital subscriber line        interface, bridge, hub, router, or other similar device and/or        software to manage such a device.    -   node—an information device coupled to a network.    -   non-PLC information device—an information device that is not a        PLC.    -   operating system—Low-level software that handles the interface        to peripheral hardware, schedules tasks, allocates storage, and        presents a default interface to the user when no application        program is running. The operating system can be considered as        split into a kernel that is always present and various system        programs that use facilities provided by the kernel to perform        higher-level house-keeping tasks, often acting as servers in a        client-server relationship. The operating system can be        considered as including a graphical user interface and a        windowing system.    -   order—to arrange and/or present.    -   parameter—a variable.    -   personal computer—a general-purpose microcomputer designed to be        operated by one person at a time.    -   PLC configuration program—a program adapted to configure a PLC.    -   PLC network—a network of communicatively coupled PLC's.    -   plurality—the state of being plural and/or more than one.    -   poll—to check status to see if a particular external event has        occurred.    -   PPI (Point to Point Interface)—a peer-to-peer data communication        interface used for operator interface connections for certain        PLC's, such as the Siemens S7-200 family of PLC's.    -   predetermined—established in advance.    -   present—to introduce, provide, show, display and/or offer for        consideration.    -   preview—to view or exhibit in advance; an introductory or        preliminary message, sample, and/or overview; a foretaste.    -   processor—a device and/or set of machine-readable instructions        for performing one or more predetermined tasks. A processor can        comprise any one or a combination of hardware, firmware, and/or        software. A processor can utilize mechanical, pneumatic,        hydraulic, electrical, magnetic, optical, informational,        chemical, and/or biological principles, signals, and/or inputs        to perform the task(s). In certain embodiments, a processor can        act upon information by manipulating, analyzing, modifying,        converting, transmitting the information for use by an        executable procedure and/or an information device, and/or        routing the information to an output device. A processor can        function as a central processing unit, local controller, remote        controller, parallel controller, and/or distributed controller,        etc. Unless stated otherwise, the processor can be a        general-purpose device, such as a microcontroller and/or a        microprocessor, such the Pentium IV series of microprocessor        manufactured by the Intel Corporation of Santa Clara, Calif. In        certain embodiments, the processor can be dedicated purpose        device, such as an Application Specific Integrated Circuit        (ASIC) or a Field Programmable Gate Array (FPGA) that has been        designed to implement in its hardware and/or firmware at least a        part of an embodiment disclosed herein.    -   Profibus (Process Field Bus)—a popular, open, and        vendor-independent type of fieldbus and/or token ring bus used        in automation technology.    -   program—a set of coded instructions that enables a machine,        especially a computer, to perform a desired sequence of        operations.    -   program block—a portion of a memory dedicated to storing one or        more programs.    -   programmable logic controller (PLC)—a device that follows        programmed instructions to evaluate a set of inputs and provide        automated monitoring and/or control of an industrial plant        and/or process. A PLC can be applied in uses comprising        materials conveying, materials pumping, materials manufacturing,        electrical power generation, electrical power distribution,        heating systems, ventilating systems, air conditioning systems,        chemical processing, mining, machining, packaging, and/or        materials distribution, etc. A PLC can be communicatively        coupled with a first network of non-information devices such as        sensors and/or actuators.

A PLC can be communicatively coupled with a second network ofinformation devices.

-   -   property—a parameter of an electronic file.    -   provide—to furnish, supply, and/or make available.    -   read—to obtain.    -   receive—to take, get, acquire, and/or have bestowed upon.    -   recipe—a plurality of input values and/or settings, each        corresponding to a process variable, and communicable to a PLC        program for operating a process.    -   recognize—to perceive or show acceptance of the validity of.    -   render—to make perceptible.    -   resident—located and/or present.    -   running—in operation.    -   search—to investigate, examine, and/or probe.    -   search parameter—a criteria to which a search is constrained.    -   select—to choose.    -   set—a related plurality.    -   size—an amount of physical and/or virtual memory occupied by an        electronic file.    -   software—a written program that is stored in volatile memory.    -   specify—to state explicitly and/or in detail.    -   storage location—a physical and/or virtual place of an        electronic file.    -   store—to place, hold, and/or retain data, typically in a memory.    -   stored on PLC network—stored on a node and/or a memory device        coupled to a node, of a PLC network.    -   substantially—to a great extent or degree.    -   system—a collection of mechanisms, devices, data, and/or        instructions, the collection designed to perform one or more        specific functions.    -   system block—a portion of a memory dedicated to storing one or        more operating system programs.    -   temporal—regarding a creation and/or modification date and/or        time.    -   textual—words treated as data by a computer.    -   user—a person interfacing with an information device.    -   user interface—any device for rendering information to a user        and/or requesting information from the user. A user interface        includes at least one of textual, graphical, audio, video,        animation, and/or haptic elements. A textual element can be        provided, for example, by a printer, monitor, display,        projector, etc. A graphical element can be provided, for        example, via a monitor, display, projector, and/or visual        indication device, such as a light, flag, beacon, etc. An audio        element can be provided, for example, via a speaker, microphone,        and/or other sound generating and/or receiving device. A video        element or animation element can be provided, for example, via a        monitor, display, projector, and/or other visual device. A        haptic element can be provided, for example, via a very low        frequency speaker, vibrator, tactile stimulator, tactile pad,        simulator, keyboard, keypad, mouse, trackball, joystick,        gamepad, wheel, touchpad, touch panel, pointing device, and/or        other haptic device, etc. A user interface can include one or        more textual elements such as, for example, one or more letters,        number, symbols, etc. A user interface can include one or more        graphical elements such as, for example, an image, photograph,        drawing, icon, window, title bar, panel, sheet, tab, drawer,        matrix, table, form, calendar, outline view, frame, dialog box,        static text, text box, list, pick list, pop-up list, pull-down        list, menu, tool bar, dock, check box, radio button, hyperlink,        browser, button, control, palette, preview panel, color wheel,        dial, slider, scroll bar, cursor, status bar, stepper, and/or        progress indicator, etc. A textual and/or graphical element can        be used for selecting, programming, adjusting, changing,        specifying, etc. an appearance, background color, background        style, border style, border thickness, foreground color, font,        font style, font size, alignment, line spacing, indent, maximum        data length, validation, query, cursor type, pointer type,        autosizing, position, and/or dimension, etc. A user interface        can include one or more audio elements such as, for example, a        volume control, pitch control, speed control, voice selector,        and/or one or more elements for controlling audio play, speed,        pause, fast forward, reverse, etc. A user interface can include        one or more video elements such as, for example, elements        controlling video play, speed, pause, fast forward, reverse,        zoom-in, zoom-out, rotate, and/or tilt, etc. A user interface        can include one or more animation elements such as, for example,        elements controlling animation play, pause, fast forward,        reverse, zoom-in, zoom-out, rotate, tilt, color, intensity,        speed, frequency, appearance, etc. A user interface can include        one or more haptic elements such as, for example, elements        utilizing tactile stimulus, force, pressure, vibration, motion,        displacement, temperature, etc.    -   user log—a record of events associated with one or more users.    -   video—humanly visible and varying images.    -   volume—a disk drive and/or virtual disk drive.    -   Windows family—any operating system having “Windows” in its name        and provided by Microsoft Corporation of Redmond, Wash.

DETAILED DESCRIPTION

Certain exemplary embodiments can comprise a method, comprising:recognizing, by a PLC, that a memory device has been connected to thePLC; and configuring the PLC via a PLC executable software programresident on the memory device. Certain exemplary embodiments cancomprise a method, comprising: via a PLC network interface: presenting aPLC network as a namespace shell extension of an operating system of anon-PLC information device; and rendering, to a user of the non-PLCinformation device, the PLC network as a node of a network. Certainexemplary embodiments can comprise a method, comprising: via a PLCnetwork interface: presenting a PLC network as a namespace shellextension of an operating system of a non-PLC information device; andsearching the PLC network for at least one item corresponding to one ormore search parameters.

Programmable logic controllers (PLCs) have traditionally been utilizedin a wide spectrum of applications from factory automation to wastewater treatment plant controls and from chemical process plant controlto engine management systems. Each application typically has a uniqueprogram, written to the user's specifications, to control the sequenceof events for that particular system.

Today, many industries use programmable logic controllers to properlyoperate and monitor elaborate industrial equipment and processes.Programmable logic controllers typically operate in accordance with astored control program that causes the controller to examine the stateof the controlled machinery and/or process by evaluating signals fromone or more sensing devices (e.g., temperature or pressure sensors), andto operate the machinery and/or process elements (e.g., by energizing orde-energizing operative components) based on a procedural framework, thesensor signals and, if necessary, more complex processing.

Information can be gathered by the PLC from various sensor inputs(analog and/or discrete). The PLC can process the data using, forexample, Relay Ladder Logic, a type of computer program based on HardWired Relay Logic. As sensor data is gathered and manipulated by theuser program, the PLC can send appropriate output signals to control theoperation of the equipment to which it is connected. The result is oftensafer, more efficient operation of the monitored or controlledequipment.

Frequently, process operation is monitored, at least intermittently, bysupervisory personnel by means of one or more central managementstations. Each station can sample the status of controllers (and theirassociated sensors) selected by the operator and/or can present the datain some meaningful format. The management station may or may not belocated on the same site as the monitored equipment; frequently, onecentral station can have access to multiple sites (whether or not theseperform related processes).

A programmable logic controller (PLC) can utilize a portable memorydevice for storage. The memory device, which can be a memory cartridge,can be an electronically erasable programmable read only memory (EEPROM)device. The memory device can be used to store one or more PLCexecutable software programs, recipes, data logs, process documentation,program documentation, user files, etc. Each of these items can bestored on the memory device as a discrete binary or text file.

The memory device can also comprise dedicated memory blocks such as aprogram block, a data block, and/or a system block. Each of these blockscan be available to the PLC for temporary storage prior to and/or duringexecution of the PLC executable software program.

Upon connection of the memory device to the PLC, the memory device canbe automatically read to detect the PLC executable software program, andcan automatically execute that program to configure the PLC.

The PLC can include a network interface that allows certain remoteinformation devices to recognize the PLC as a node of a network, such asa PLC network. The PLC and/or the remote information devices cancomprise interface software that can allow the remote informationdevices to interpret the PLC network, PLC, memory cartridge, filestructure of the memory cartridge, and/or files themselves, in a mannerconsistent with the operating system of the remote information device.

Thus, for example, a remote information device can run the Windows XPoperating system, and can interpret and/or render the PLC, memorydevice, and/or contents of the memory device as a network node, device,volume, folder, file, and/or item in a hierarchical path. As anotherexample, a memory cartridge can appear in Windows Explorer (or any otherpath-rendering human interface) as an item of a hierarchical pathcomprising the PLC network, the PLC, the memory cartridge, and/or thememory cartridge contents (which can be rendered and/or treated asfiles).

The PLC interface software residing on the information device can allowa user to treat files residing on the memory device in the same manneras files residing on and/or in any other recognizable node, device,volume, folder, etc. Thus, the user can copy files to and/or from thememory device, delete files from the memory device, rename files on thememory device, etc.

Moreover, the PLC interface software can support multiple instances ofthe files, so that multiple windows can be displayed providing the sameor different views of those files.

By presenting the PLC network, PLC, memory cartridge, file structure ofthe memory cartridge, and/or files stored on the memory cartridge in amanner recognizable by the operating system of the remote informationdevice, the PLC interface software can allow a user, via thecapabilities built-in to the operating system of the remote informationdevice, to perform a search for files residing on and/or in the PLCnetwork, PLC, memory cartridge, etc. Thus, for example, a user cansearch for any file that, for example, has “flowchart” in its name, hasa “.pdf” extension, was created before 20 Jan. 2005, was modified after24 Jan. 2005, has a particular icon associated therewith, etc. Thesearch can return a list of files that conform to the search criteria.

Moreover, utilizing the search capabilities of the operating systemand/or other software loaded on the remote information device, the PLCinterface software can allow the user to perform a search of thecontents of the files residing on and/or in the PLC network, PLC, memorycartridge, etc. Thus, for example, a user can search for all mentions ofthe phrase “T-101 High Level Alarm” in any file located on any PLCand/or memory cartridge visible from the remote information device. Thesearch can return a list of files that conform to the search criteriaand/or highlight, preview, and/or otherwise identify the portion of thefile that contains the text, graphic, photograph, audio clip, video,etc. that corresponds to the search parameters.

FIG. 1 is a block diagram of an exemplary embodiment of a system 1000,which can comprise one or more PLC's 1100. Any given PLC 1100 cancomprise a processor 1100, a memory 1120, an I/O interface 1130, amemory device recognizer 1140, a PLC configurator 1150, a networkinterface 1160, and/or a processing system I/O interface 1170.

A memory cartridge and/or device 1200, which can store a PLCconfiguration program, can be inserted into, plugged into, coupled to,connected to, received by, etc., PLC 1100, where memory device 1200 canbe recognized and/or read by memory device recognizer 1140. Memorydevice 1200 can comprise a plastic, polycarbonate, metal, aluminum, etc.housing and/or one or more EEPROMs, flash drives, and/or hard drives.Memory device 1200 can have a storage capacity ranging fromapproximately 8 KB to 128 GB, and possibly greater, including all valuesand subranges therebetween. Memory device 1200 can have a data transferrate of from approximately 8 KB/sec to approximately 128 MB/sec, andpossibly greater, including all values and subranges therebetween.Memory device 1200 can be small, lightweight, compact, portable,removable, hot-swappable, high-speed, and/or plug-and-play. Memorydevice 1200 can conform to the CompactFlash, SD, Mini SD, MultiMediaCard(MMC), RS-MMC, MemoryStick, MemoryStick PRO, MemoryStick DUO,MemoryStick PRO DUO, Smart Media, XD, USB, USB 2.0, Firewire, Firewire800, and/or SCSI, etc. formats. Memory device 1200 can utilize security,encryption, and/or certification software, such as AES, to safeguard anyfiles and/or data stored thereon.

An input/output device 1300, such as a monitor, keyboard, mouse,printer, etc., can be coupled to I/O interface 1130 of PLC 1100. Toprocessing system input/output interface 1170 can be coupled aprocessing system 1600, which can contain a plurality of sensors,actuators, etc. which can comprise, be comprised by, and/or beassociated with machinery and/or process elements.

To network interface 1160 can be coupled a network 1400, such as a PLCnetwork. To network 1400 can be coupled one or more non-PLC informationdevices 1500, which can store, utilize, and/or operate a PLC networkinterface 1520, PLC network communications interface 1540, and/or PLCnetwork user interface 1560, etc.

FIG. 2 is a flowchart of an exemplary embodiment of a method 2000. Atactivity 2100, a memory cartridge and/or device can be inserted into,plugged into, coupled to, connected to, received by, etc., a PLC. Atactivity 2200, the PLC and/or a memory device recognizer stored on amemory of, associated with, and/or coupled to, etc., the PLC, canrecognize the memory device. At activity 2300, the memory device can beread and/or a PLC configuration program stored on the memory device canbe an be identified, recognized, and/or selected from among a pluralityof PLC executable software programs resident on the memory device. Atactivity 2400, the PLC configuration program stored can be executed. Atactivity 2500, one or more parameters associated with the PLC, and/orone or more values for each of those parameters, can be identified,determined, and/or set by the PLC configuration program, and/or the PLCcan be configured to conform with those values for those parameters.

FIG. 3 is a flowchart of an exemplary embodiment of a method 3000. Atactivity 3100, a PLC network interface associated with a non-PLCinformation device can poll for networks (such as one or more PLCnetworks) and/or devices coupled to each network, such as a PLC and/or amemory device coupled to a PLC. At activity 3200, the PLC networkinterface can identify one or more PLC networks, addresses of eachnetwork, and/or one or more devices coupled to each network. At activity3300, communications parameters and/or values therefore can be exchangedbetween the PLC network interface and the PLC network and/or devicescoupled thereto, the PLC network interface and the PLC network and/ordevices coupled thereto can be communicatively coupled, and/orcommunications can occur between the PLC network interface and anidentified PLC network and/or device coupled thereto.

At activity 3400, a PLC network can be presented to and/or interpretedby a non-PLC information device as a namespace shell extension of arunning operating system of the non-PLC information device. Theoperating system can be a personal computer operating system, such as amember of the Windows family of operating systems (e.g., Windows 2000,Windows NT, Windows XP, etc.), the Macintosh family of operating systems(OS 9, OS X, etc.), Linux, Unix, Solaris, etc. For each recognizeddevice coupled to the PLC network, a PLC network address can be providedto, received by, and/or determined by the PLC network interface. Asneeded, multiple instances of the PLC network and/or devices coupledthereto can be provided.

At activity 3500, a PLC network and/or devices coupled thereto can berendered to a user of a non-PLC information device. For example, a PLCnetwork can be rendered as a volume, directory, folder, and/or apredetermined icon, such as a network icon. As another example, a folderitem can be rendered for each device coupled to the PLC network and/oreach file stored on such a device. The folder item can be rendered as avolume, directory, folder, and/or a predetermined icon, such as a PLCand/or a PLC memory device icon. Thus, the PLC network, PLC's, PLCmemory devices, and/or PLC memory device files can be renderedhierarchically, as a hierarchical structure, and/or as a path. Folderitems can be rendered in any order, such as by PLC network address(e.g., Profibus, PPI, and/or Ethernet address, etc.), by item type, inalphabetical name order, in date created order, in date modified order,and/or in size order, etc.

At activity 3600, a user can be empowered and/or permitted to browse aPLC network, such as by using a file browser such as Windows Explorerand/or Macintosh Finder, etc., and/or by using an IP browser such asInternet Explorer, FireFox, and/or Safari, etc.

At activity 3700, information stored on a device coupled to a PLCnetwork can be identified to a user of the non-PLC information device,and/or information can be transferred between a PLC network, a devicecoupled to a PLC network, and/or a non-PLC information device. Anappropriate graphic can be rendered in response to a user of the non-PLCinformation device issuing a command regarding such information. Forexample, an icon and/or animation can be rendered indicating progress intransferring a file from (or to) a PLC memory device to (or from) thenon-PLC information device.

FIG. 4 is a flowchart of an exemplary embodiment of a method 4000. Atactivity 4100, a PLC network can be presented to and/or interpreted by anon-PLC information device as a namespace shell extension of a runningoperating system of the non-PLC information device. For each recognizeddevice coupled to the PLC network, a PLC network address can be providedto, received by, and/or determined by the PLC network interface. Asneeded, multiple instances of the PLC network and/or devices coupledthereto can be provided. A PLC network, PLC's, PLC memory devices,and/or PLC memory device files can be rendered, to a user of the non-PLCinformation device, in any of numerous manners, such as hierarchically,as a hierarchical structure, and/or as a path, etc.

At activity 4200, the user can enter, and/or a PLC network interfaceassociated with a non-PLC information device can receive from the user,values for one or more search parameters of interest to the user forsearching one or more items, such as one or more PLC networks, PLC's,PLC memory devices, PLC memory device files, and/or content and/ormetadata thereof, etc. Any of numerous search parameters can beselectable, including, for example, a property of the item, an addressof an item, any portion of an item name, an item type, item creationinformation, item modification information, temporal information, itemstorage information, item size, a textual content of an item, agraphical content of an item, an image content of an item, an audiocontent of an item, a video content of an item, an animation content ofan item, etc. For example, a user can search for any files containingmentions of the words “asbestos”, “carcinogen”, “hazardous”, “mercury”,and/or “lead”.

At activity 4300, the PLC network interface can initiate a search forand/or of one or more PLC networks, PLC's, PLC memory devices, PLCmemory device files, and/or content and/or metadata thereof, etc., thatcorresponds, at least in part, to the provided values of the searchparameters, and/or any matches can be identified and/or provided to thePLC network interface.

At activity 4400, at least a portion of the items identified by thesearch can be rendered to the user, such as via the PLC networkinterface. Any identified item can be rendered in a manner that aportion of an item that caused the item to be considered a match can behighlighted, rendered in context, and/or previewed. For example, 25words on either side of any mentions of the search terms “asbestos”,“carcinogen”, “hazardous”, “mercury”, and “lead” can be rendered. Theitems of the search results can be weighted and/or ranked. The items ofthe search results can be rendered in any order, such as by rank, name(alphabetically), type, size, creation date, modification date, etc.

At activity 4500, the user can access one or more of the search resultsand/or associated information, such as via the PLC network interface.For example, by double-clicking on any item rendered as a search result,a user can be provided with additional information about that item. Ifthe item is a file, the file can be opened, perhaps to the location atwhich the match occurred.

FIG. 5 is a block diagram of an exemplary embodiment of an informationdevice 5000, which in certain operative embodiments can comprise, forexample, PLC 1100 and/or non-PLC information device 1500 of FIG. 1.Information device 5000 can comprise any of numerous well-knowncomponents, such as for example, one or more network interfaces 5100,one or more processors 5200, one or more memories 5300 containinginstructions 5400, one or more input/output (I/O) devices 5500, and/orone or more user interfaces 5600 coupled to I/O device 5500, etc.

In certain exemplary embodiments, via one or more user interfaces 5600,such as a graphical user interface, a user can view a rendering ofinformation related to a PLC network and/or a PLC.

S7-200 Explorer

Certain exemplary embodiments are referred to herein as the “S7-200Explorer”, which can integrate with Microsoft Windows Explorer and/orMicrosoft Internet Explorer to allow the user to browse their S7-200network and/or the contents of each PLC on the network. The remainder ofthis Detailed Description describes various potential aspects of certainexemplary embodiments of S7-200 Explorer.

Terminology used in this portion of the Detailed Description DescriptionAccess Point A standard S7DOS term that refers to the set ofcommunications devices and protocols available to a specificapplication. Each SIMATIC application generally can have a unique accesspoint. Namespace A COM server that represents a hierarchical storage ofShell objects, and can be accessed by Windows Shell clients Extensionsuch as Windows Explorer and Windows Internet or NSE Explorer. Explore AWindows standard term that refers to viewing namespaces and theirsubfolders in the “left” pane (or folder view in Window InternetExplorer) of Windows Explorer. Individual items that have no sub itemrepresentations (like a file) need not be shown in the Explore view.Open A Windows standard term that refers to viewing a folder's contentsin the “right” pane of Windows Explorer. This view shows BOTH files andsub folders that can be contained in the currently “explored” item.“Open” can be effectively a “look inside” the object. Context Menu Apopup menu displayed automatically in response to a right mouse buttonclick. The contents of the menu can be context-specific to the locationwhere the user clicked. Gen 3 MC The 256 KB & 64 KB memory cartridgeavailable for use with S7-22X G2E PLCs. This can be the memory cartridgethat can be “opened” using the S7-200 Explorer. The older memorycartridges Gen 1 (8k & 16k) and the Gen 2 (32 KB) can be detected andneed not be displayed in S7-200 Explorer. GPB General Purpose Block. Ablock that contains memory cartridge directory information in Area 1 anduser file data in Area 3. UDM Upload Download Manager. Multifaceteddialog in Microwin that manages the Programming of a memory cartridgevia the PLC as well as Upload, Download, and Clear operations. Tree NodeAn item listed in the tree view of the S7-200 Explorer which can have nosub items. Tree Folder An item listed in the tree view of the S7-200Explorer which can have subitems. In the tree view, the term folder canbe used to indicate an item that can be “explored” or “opened” to viewits contents.

Functional Specification

This subsection describes the potential appearance and/or functionalityof certain exemplary embodiments of S7-200 Explorer.

Product Deployment

Certain exemplary embodiments of S7-200 Explorer can be availablethrough either of two channels:

-   -   The S7-200 Explorer can ship and install as a standard addition        to STEP 7-Micro/WIN Version 4.0. It can be included on the same        setup CD as STEP 7-Micro/WIN, and/or can be automatically        installed along with STEP 7-Micro/WIN, with no additional user        interaction.    -   The S7-200 Explorer can also be made available as a free        internet download. Users need not have to purchase STEP        7-Micro/WIN in order to obtain, install, and/or use the S7-200        Explorer. When the product is installed from an internet        download, a minimal setup interface can be supplied so that the        user can customize their installation.

Installation Options

When certain exemplary embodiments of S7-200 Explorer are installed froman internet download, the user can be asked to specify the followinginformation:

-   -   Installation Directory—The user need not necessarily be provided        the option to select the drive/directory where S7-200 Explorer        will be installed. The default directory can be C:\Program        Files\Siemens\S7-200 Explorer.    -   National Language—The user can have the option to select which        National Language will be used for the S7-200 Explorer        interface. The S7-200 Explorer can install any of the national        languages supported by STEP 7-Micro/WIN. The user can be asked        to choose which language they wish to use on install. The        default choice for this selection can be the national language        chosen for the setup.

When S7-200 Explorer can be implicitly installed as part of the STEP7-Micro/WIN installation, the installation directory can be a peer ofthe directory where STEP 7-Micro/WIN was installed, and/or can be namedS7-200 Explorer. The national language for S7-200 Explorer canautomatically be set to the national language selected by the setupscript for STEP 7-Micro/WIN.

Installation Artifacts

Installing certain exemplary embodiments of S7-200 Explorer (in eitherof the manners described above) can cause the following changes to theuser's system:

Start Menu

The user's Start Menu can be updated to include choices for My S7-200Network and/or S7-200 Explorer Help. These two choices can appear in theS7-200 Explorer V1.0 folder, which in turn can be placed under theSIMATIC Folder. The SIMATIC folder can act a container for SIMATICsoftware on the user's machine. In this regard, S7-200 Explorer canappear as a peer to any installed versions of STEP 7-Micro/WIN. FIG. 6illustrates the Start menu for an exemplary embodiment of an independentinstallation of S7-200 Explorer. Note that some details of this screencapture can be specific to Windows 2000®. The Windows XP® Start menu canhave a slightly different appearance.

Desktop Shortcuts

S7-200 Explorer can place two shortcuts on the user's desktop, that canmatch the items added to the start menu. FIG. 7 provides an illustrationof exemplary embodiments of the icons for these shortcuts.

PG/PC Interface

S7-200 Explorer can install the same communication support as STEP7-Micro/WIN, no matter which installation option is used. Further,S7-200 Explorer can use the same communications access point as STEP7-Micro/WIN. Therefore, any change to the communications settings whileworking in one can affect the other.

Change/Remove Installation

S7-200 Explorer can have a separate entry in the Add/Remove Programsdialog, as illustrated in the exemplary embodiment shown in FIG. 8.Clicking the Change/Remove button can launch the Installshield® wizardfor the S7-200 Explorer. From this dialog the user can have thefollowing options:

-   -   Remove the current installation. This option can allow the user        to uninstall the S7-200 Explorer.

Operating System Dependencies/Compatibility

S7-200 Explorer can install and operate on all operating systems/OSversions supported by STEP 7-Micro/WIN v4.0.

STEP 7-Micro/WIN Dependencies/Compatibility

S7-200 Explorer can install all the components necessary for its ownoperation. It need have no component or DLL dependency on a specificversion of STEP 7-Micro/WIN. For this reason, it can be compatible withall existing versions of STEP 7-Micro/WIN.

Compatibility with Other SIMATIC Products

S7-200 Explorer need have no specific compatibility issues with otherSIMATIC products. It can co-exist with other SIMATIC applications to thesame degree as STEP 7-Micro/WIN v4.0.

The “My S7-200 Network” Namespace

“My S7-200 Network” can be a Windows namespace shell extension (NSE)that allows the user to explore the “contents” of their S7-200 networkin the same manner they would explore their file system. The “My S7-200Network” NSE can appear as a hierarchical container that can be accessedfrom Windows Explorer. Examples of common namespaces used in Windows canbe “Control Panel”, “My Computer”, “My Network Places”, etc. Namespacescan contain namespaces below them as well. The ability to integrate intothe Windows shell can give some unique opportunities to allowMicrosystems control interfaces to have the look and feel of being apart of the Window's experience for users as well as some uniqueintegration capabilities such as scheduling upload of Data Logs.

Accessing “My S7-200 Network”

Once the S7-200 Explorer has been installed on the user's system, the“My S7-200 Network” NSE can appear as a node under “My Computer” inWindows Explorer. Therefore, any time the user launches Windows Explorerthey can have access to the “My S7-200 Network”. The user can also havethe ability to specifically launch the My S7-200 Network NSE througheither the Start Menu or the Desktop icon. Note that in either of thesecases, the Windows Explorer Shell can be launched with My S7-200 Networkas the “root” node.

General Statement Regarding Windows® Standard Operations

The My S7-200 Network NSE can integrate with Windows Explorer in acompletely seamless manner. With this integration can come much standardbehavior that need not necessarily be detailed here. As a general rule,the My S7-200 Network namespace can behave in a completely standardmanner, supporting the same keyboard and mouse behavior as other Windowsnamespaces. This application describes some of the functionality andbehavior specific to My S7-200 Network, and any instances where thestandard behavior of Windows namespaces can be overridden. Where thisapplication fails to detail specific functionality, it can be assumed tomatch the Windows standards.

It can also be stated that standard Windows appearances and behaviorscan differ somewhat between different Windows versions. Again, thisapplication need not attempt to detail the differences in standardbehavior and appearance between the different versions. The screencaptures in this application were created on a personal computer runningWindows 2000®.

The Namespace Item

When the namespace is accessed, My S7-200 Network can appear as a node.It might or might not appear as the root item in the interface,depending on the method used to launch the namespace. FIG. 9 shows theappearance of an exemplary embodiment of a namespace when launched aspart of the “My Computer” namespace in Windows Explorer. Note that theact of launching the namespace as a part of My Computer does notnecessarily cause the namespace to be “explored”. Therefore the MyS7-200 Network item can appear as a node.

Context Menu

In certain exemplary embodiments, when the user selects the My S7-200Network item and clicks the right mouse button, a context menu can bedisplayed showing available options. What follows is a description ofcertain exemplary embodiments of each menu option, what it does, and therules governing its availability.

-   -   Expand/Collapse—This can be the default option supplied by        Windows XP® for all namespace items. It causes the contents of        the selected item to be displayed in the right-hand pane of the        Explorer view or collapsed into a tree node.    -   Explore—This opens a new Explorer window. The Folder view can be        the same, but the item can be expanded in the right-hand view of        this new Explorer window.    -   Open—This menu item can display the contents of the PLC item in        a separate Explorer view, without the left-hand Folder view.    -   Modem Connect—This menu item can only appear when the user's        current communications settings specify a modem connection. This        menu item can launch the Modem Connection dialog. Note that this        menu item can appear as “Modem Disconnect . . . ” if the modem        connection is currently active. Selecting this menu choice can        cause a refresh of the namespace.    -   Modem Setup—This menu item can appear when the user's current        communications settings specify a modem connection. This menu        item can launch the Modem Setup dialog. Selecting this menu        choice can cause a refresh of the namespace.    -   PG/PC Interface—This menu choice can be visible for the        namespace item. It launches the PG/PC Interface dialog.        Selecting this menu choice can cause a refresh of the namespace.    -   Add IP Address—This menu choice can appear when the user's        current communications settings specify Ethernet communications.        This menu item can launch the IP Address Browser dialog.        Selecting this menu choice can cause a refresh of the namespace.    -   Create Shortcut—This menu choice can be used to create a Windows        shortcut to the namespace item. This shortcut can by default be        placed on the desktop.    -   Properties—This menu choice displays the property sheet for the        namespace item. This is described in more detail in the        following section.    -   Help—This menu choice can launch help for the S7-200 Explorer.

Namespace Properties

When the user selects “Properties” from the context menu for thenamespace item, the properties dialog of FIG. 10 can be displayed. Thisproperties dialog contains the product version and a read-only displayof the current communications parameters. This display can be modeledafter the information displayed in the STEP 7-Micro/WIN Communicationsdialog. The information shown above can be appropriate for a PPIconnection. Other types of connections (e.g., Ethernet) can showslightly different information.

Double Click Support

The behavior of the double mouse click on the namespace item can be thesame as selecting “Expand” from the context menu.

Expanding the Namespace Contents

Whenever the namespace is refreshed (either explicitly by selectingRefresh from the Windows Explorer main menu, or implicitly by selectinga context menu choice), the contents of My S7-200 Network can bedetermined by activating the communications interface currently selectedby the user. The resulting view can be very similar to the network lifelist displayed in the STEP 7-Micro/WIN “Communications” dialog. Thescreen capture of FIG. 11 shows an example S7-200 network with all thepossible types of items detected.

The My S7-200 Network can be now displayed as a folder containing anitem for each device on the network. The items in the My S7-200 Networkfolder can be ordered by network address. When the user has Ethernetcommunications selected, the addresses can appear as such. FIG. 11illustrates an example S7-200 Ethernet network.

No matter what the network type, the devices on the network can belisted in order of network address. There can be four distinctcategories of items that can be listed in the namespace. The followingsections detail the functionality of each.

PLC Items

S7-200 PLCs on the network can appear as items in the namespace folder.The label for each PLC in the folder view (the left-hand pane of theExplorer interface) can comprise the network address (either Profibus orEthernet) in parenthesis followed by the PLC model and firmwarerevision, read from the PLC. Specific icons can be provided for each PLCtype. Note that the 16×16 (small) icons can be all the same for all PLCtypes. FIG. 12 lists the possible PLC icons (32×32 pixel version) thatcan appear in the namespace, and their associated PLC types. The PLCitem can appear with or without the expansion indicator (the “+” sign).The expansion indicator can be present if the PLC has an attached Gen 3memory cartridge.

Context Menu

Right clicking on a PLC item (in either the left or right pane of theexplorer view) can display a context menu of available options. Whatfollows are descriptions of each potential menu option, what it does,and the rules governing its availability.

-   -   Expand/Collapse—This can be the default option supplied by        Windows XP® for all namespace items. It causes the contents of        the selected item to be displayed in the right-hand pane of the        Explorer view.    -   Explore—This opens a new Explorer window. The Folder view can be        the same, but the item can be expanded in the right-hand view of        this new Explorer window.    -   Open—This menu item can display the contents of the PLC item in        a separate Explorer view, without the left-hand Folder view.    -   Modem Connect—This menu item can appear when the user's current        communications settings specify a modem connection. This menu        item can launch the Modem Connection dialog. Note that this menu        item can appear as “Modem Disconnect . . . ” if the modem        connection is currently active. Selecting this menu choice can        cause a refresh of the namespace.    -   Modem Setup—This menu item can appear when the user's current        communications settings specify a modem connection. This menu        item can launch the Modem Setup dialog. Selecting this menu        choice can cause a refresh of the namespace.    -   PG/PC Interface—This menu choice can always be visible for the        namespace item. It launches the PG/PC Interface dialog.        Selecting this menu choice can cause a refresh of the namespace.    -   Add IP Address—This menu choice can appear when the user's        current communications settings specify Ethernet communications.        This menu item can launch the IP Address Browser dialog.        Selecting this menu choice can cause a refresh of the namespace.    -   Create Shortcut—This menu choice can be used to create a Windows        shortcut directly to the PLC item. This shortcut can by default        be placed on the desktop.    -   Help—This menu choice can launch help for the S7-200 Explorer.

TD 200 Items

When the user has PPI communications selected, TD 200 devices (firmwareversion 2.01 and later) attached to the network can appear in thenamespace.

Context Menu

The context menu for TD 200 items can be the same as is displayed forPLC items. Note that TD 200 devices typically only appear in thenamespace when a non-Ethernet communications option is selected, so the“Add IP Address . . . ” choice need not appear in the context menu for aTD 200 item.

Also, no additional information typically is available for TD 200 items,so nothing typically is gained by using the Expand, Explore, or Opencontext menu choices. These menu choices can still perform in theexpected manner (as you would expect for an empty folder in WindowsExplorer), but no additional information can be displayed.

Unknown Items

When a device responds to a poll of its address, but does not answer arequest to read SD0, the device can be displayed as an “unknown” item inthe namespace. This might include S7-300 PLCs, Operator panels, or TD200 devices older that version 2.01. However, since the device did notanswer the SD0 read request, no type or version information typically isavailable for the device.

Context Menu

The context menu for Unknown items can be the same as is displayed forPLC items. Unknown items can appear for any communications option, sothe menus options described earlier can apply.

As with the TD 200 device, no additional information is typicallyavailable for Unknown items, so nothing is necessarily gained by usingthe Expand, Explore, or Open context menu choices. These menu choicescan still perform in the expected manner (as you would expect for anempty folder in Windows Explorer), but no additional informationtypically would be displayed.

Not Present Items

When the user is communicating through an Ethernet interface, thenetwork typically is not polled to determine present devices. Rather,the user typically configures the addresses they wish to see (using theIP Address Browser dialog in either STEP 7-Micro/WIN or available fromcontext menus in the namespace). If the user configures a networkaddress for which no device is found, the address can be displayed as a“<not present>” node. This can mimic what occurs in the STEP 7-Micro/WINcommunications dialog for the same situation.

Context Menu

The context menu for ‘Not Present’ items can be the same as is displayedfor PLC items.

No additional information is typically available for ‘Not Present’items, so nothing typically is gained by using the Expand, Explore, orOpen context menu choices. These menu choices can still perform in theexpected manner (as you would expect for an empty folder in WindowsExplorer), but no additional information need be displayed.

PLC Block Items

PLC Items can be expanded to view the block contents of the PLC device.This information can be displayed in the following ways:

-   -   Single clicking or double clicking the left mouse button on the        PLC Block Item can cause the contents of the PLC device to be        listed in the right pane of the explorer view. FIG. 13        illustrates this.    -   Selecting the context menu choice Explore can produce the same        display of information, but can launch a new Explorer window for        the display. The existing Explorer view can be unaffected.    -   Selecting the context menu choice Open can also open a new        Explorer view, but display the information without the Folder        view, as illustrated in FIG. 14.

A PLC can contain the following items:

Information Item Name Rules Available Description 256K Memory Presentonly if the PLC Size The total amount of Cartridge has an attached 256KB used that exists (used + Gen 3 cartridge. available) on the cartridge64K Memory Present only if the PLC Size The total amount of Cartridgehas an attached 64 KB used that exists (used + Gen 3 cartridge.available) on the cartridge Program Block Present only if the PLC SizeThe total size OB1 has an OB1 block. Modified The modified This blockmight or timestamp for OB1 might not be present Created The createdtimestamp for OB1 Data Block Present only if the PLC Size The total sizeof DB1 has a DB1 block. This Modified The modified block might or mighttimestamp for DB1 not be present Created The created timestamp for DB1System Block The PLC always has a Size The total size of the SystemBlock. SDB Depending on the Modified The modified situation, this can betimestamp for the SDB SDB0 or SDB2 Created The created timestamp for theSDB

Any items present can be listed in the order above.

Context Menu

The context menu for PLC Block items contains a single choice for“Properties”. Double-clicking on the PLC Block item can also launch theproperties dialog.

Properties Dialog

When the user selects “Properties” from the context menu for a PLC Blockitem, the properties dialog shown in FIG. 15 can be displayed. Note thatthe various sizes in the screen capture are for example purposes only.For an actual block, the Total Size field can represent the sum of theHeader size, Area 1 size and Area 3 size.

This properties dialog can have the following features:

-   -   The Title of the dialog can be the name of the PLC block item        plus ‘Properties’    -   The top area of the dialog can repeat the PLC block name, and        display the icon used for PLC blocks in STEP 7-Micro/WIN.    -   The Total size field can display the size of the block on the        PLC. Note that this can be the total size of the block, not just        the Area 1 size.    -   The Created field can be the created time for the PLC block.        This date and time can be formatted in the same manner as        timestamps within the Windows file properties sheet.    -   The Modified field can be the modified time for the PLC block.        This date and time can be formatted in the same manner as        timestamps within the Windows file properties sheet.

Gen 3 Memory Cartridge Items

If a PLC device on the network has an installed Gen 3 memory cartridge,then the PLC item can be displayed with the expansion indicator (+).Clicking the expansion indicator can update the left-hand “Folders” paneto show the Gen 3 memory cartridge. This action does not affect theright-hand pane of the Explorer view.

Context Menu

The 256K-memory cartridge item can display the following in its contextmenu.

-   -   Expand—This can be the default option supplied by Windows XP®        for all namespace folder items. In the case of the memory        cartridge this can be disabled because there are no subfolder        objects underneath it to expand to.    -   Explore—This opens a new Explorer window. The Folder view can be        the same, but the item can be expanded in the right-hand view of        this new Explorer window.    -   Open—This menu item can display the contents of the PLC item in        a separate Explorer view, without the left-hand Folder view.    -   Clear All—This menu choice allows the user to clear the contents        of the Gen 3 memory cartridge. Since this can be a destructive        action and typically is not un-doable, the user can be asked to        confirm this choice.    -   Create Shortcut—This menu choice can be used to create a Windows        shortcut directly to the Gen 3 memory cartridge item. This        shortcut can by default be placed on the desktop.    -   Properties—This menu choice can open the properties dialog for        the memory cartridge.    -   Help—This menu choice can launch help for the S7-200 Explorer.

The Memory Cartridge Properties, shown in the screen capture of FIG. 16,can indicate the contents of the memory cartridge along with the currentdistribution in both bytes and percent of total memory cartridge space.The items can be color coded and sorted by type. Percentages less than1% can be represented by <1% symbol. The percents might not add upexactly to 100% because of rounding calculations. User and Available canalways total 100%. Byte sizes listed above the line can always total the“Used” value and the “Used” value plus the “Available” value can alwaystotal the total memory cartridge size.

-   -   Program Block—Total size of Program Block stored in the MC.    -   Data Block+V-Memory—Total size of V Memory image which the PLCs        can store anytime a Data Block is copied to the MC. Data Block        and V-Memory image can overlap and size typically is always        V-Memory of the PLC that programmed the cartridge+Data Block        Area 3 & header.    -   System Block+Output Tables—Total size of System block plus 300+        bytes taken up by the output tables.    -   PLC/Overhead—Primarily GPB overhead+a little of the PLC data        overhead.    -   Recipes—Each recipe can be listed individually by user defined        wizard name.    -   Data Logs—Each Data Log can be listed individually by user        defined wizard name.    -   User Files—Each user file stored on the memory cartridge can be        shown individually. The size can be the actual compression size        used.

Expanding a Memory Cartridge Item

The memory cartridge item can be a folder much like the PLC item. Thecontents of the memory cartridge item can be displayed in the followingways:

-   -   Single clicking or double clicking the left mouse button on the        Gen 3 memory cartridge Item can cause the contents of the memory        cartridge device to be listed in the right pane of the explorer        view. The screen capture of FIG. 17 illustrates this.    -   Selecting the context menu choice Explore can produce the same        display of information, but can launch a new Explorer window for        the display. The existing Explorer view can be unaffected.    -   Selecting the context menu choice Open can also open a new        Explorer view, but display the information without the        hierarchical Folder view, as illustrated in FIG. 18.

Expanded Memory Cartridge Contents

Once the Gen 3 memory cartridge item has been expanded, the followingitems can be listed:

Information Item Name Rules Available Description Program Block Presentonly if the MC Size The size of the entire has been programmed OB1 inthe MC with OB1 from the PLC. Modified The modified timestamp This blockmight or for OB1 might not be present Created The created timestamp forOB1 Data Block Present only if the MC Size The size of the entire hasbeen programmed DB1 in the MC DB1 from the PLC. This Modified Themodified timestamp block might or might for DB1 not be present. CreatedThe created timestamp for DB1 System Block Present only if the MC SizeThe size of the entire has been programmed SDB in the MC with SDB0 fromthe Modified The modified timestamp PLC. This block might for SDB ormight not be present. Created The created timestamp for SDB Recipes TheMC can contain 0 Size The size of recipe (see to 4 recipe configurationon the MC description configurations. Each Modified The modifiedtimestamp below) recipe configuration can for the recipe be listedseparately. configuration. Created The created timestamp for the recipeconfiguration. Data Logs The MC can contain 0 Size The size of data log(see to 4 data log configuration on the MC description configurations.Each Modified The modified timestamp below) data log configuration forthe recipe can be listed separately. configuration. Created The createdtimestamp for the recipe configuration. Files The MC can contain 0 SizeThe compressed size of (see or more data files. Each the file.description data file on the MC can Modified The modified timestampbelow) be listed separately. for the file. Stored files can be CreatedThe created timestamp compressed if they save for the file. at least onebyte of data otherwise they can be stored uncompressed.

Memory Cartridge contents can be listed in the order of the above table.Specific ordering within item groups are covered in the followingsections.

PLC Block Items

The PLC Block items listed in the Gen 3 memory cartridge (Program Block,Data

Block, System Block) typically support no additional functionality andtypically cannot be expanded or opened. The context menu provided forPLC Block items can contain a “Properties” option. Double-clicking theleft mouse button on a PLC Block item can also launch the propertiesdialog.

Properties Dialog

When the user selects “Properties” from the context menu for a PLC blockitem, the same properties dialog can be displayed as detailed in the PLCBlock section earlier.

Recipe Items

The Gen 3 memory cartridge item can contain (0-4) recipe items, each ofwhich corresponds to a STEP 7-Micro/WIN wizard configuration. Recipeconfigurations present on the MC can be listed individually, ordered bytheir recipe number. It can be noted that recipe configurations can becreated either with the recipe wizard or the TD 200 wizard in STEP7-Micro/WIN.

-   -   The Icon displayed for recipe items can be the same icon used in        the recipe wizard in STEP 7-Micro/WIN.    -   The Name for a recipe item can be the name the user assigned to        the wizard configuration in STEP 7-Micro/WIN. Appended to this        name in parenthesis can be the recipe number, in the form “(RCP        x)” where “x” can be 0 to 4.    -   The Size for a recipe item can be the total amount of memory        cartridge space occupied by the recipe.    -   The Modified time for a recipe item can be the last time the        wizard configuration was edited in STEP 7-Micro/WIN. Note that        this does not represent the download time.    -   The Created time for a recipe item can be the time when the        wizard configuration was created in STEP 7-Micro/WIN.

Recipe items support no additional functionality and cannot be expandedor opened. The context menu provided for Recipe items can contain a“Properties” option. Double-clicking the left mouse button on a Recipeitem can also launch the properties dialog

Properties Dialog

When the user selects “Properties” from the context menu for a recipeitem, the properties dialog of FIG. 19 can be displayed.

This properties dialog can have the following features:

-   -   The Title of the dialog can be the name of the recipe item plus        ‘Properties’    -   The top area of the dialog can repeat the recipe item name, and        display the icon used for the recipe wizard in STEP 7-Micro/WIN.    -   The size field can display the size of the recipe configuration        in the memory cartridge.    -   The Data Sets field can display the number of recipe data sets        associated with this recipe configuration.    -   The Created field can be the created time for the recipe        configuration. This date and time can be formatted in the same        manner as timestamps within the Windows file properties sheet.    -   The Modified field can be the modified time for the recipe        configuration. This date and time can be formatted in the same        manner as timestamps within the Windows file properties sheet.

Data Log Items

The Gen 3 memory cartridge item can contain (0-4) data log items, eachof which corresponds to a STEP 7-Micro/WIN data log wizardconfiguration. Data log configurations present on the MC can be listedindividually, ordered by their data log number.

-   -   The Icon displayed for data log items can be the same icon used        in the data log wizard in STEP 7-Micro/WIN.    -   The Name for a data log item can be the name the user assigned        to the data log wizard configuration in STEP 7-Micro/WIN.        Appended to this name in parenthesis can be the data log number,        in the form “(DAT x)” where “x” can be 0 to 4.    -   The Size for a data log item can be the total amount of memory        cartridge space occupied by the data log.    -   The Modified time for a data log item can be the last time the        data log wizard configuration was edited in STEP 7-Micro/WIN.        Note that this does not represent the download time.    -   The Created time for a data log item can be the time when the        data log wizard configuration was created in STEP 7-Micro/WIN.

Context Menu

Data Log items can display the following in their context menu:

-   -   Upload—This menu choice can allow the user to upload the logged        data for this item from the memory cartridge. This is discussed        in greater detail below. Double-clicking the item with the left        mouse button can have the same affect.    -   Open File on Upload—This menu choice can toggle the selection        shown. When checked this indicated when the user upload from the        namespace, the uploaded CSV file can be opened with the        currently registered CSV file editor (normally Excel). If not        checked, the Data Log can still be uploaded but the editor need        not be opened. If run from a short cut, this selection can have        no effect and the CSV editor is not opened and any error        received can be written to the CSV file rather than displayed        since the users might not be present (see Shortcuts & Automated        Uploads).    -   Create Shortcut—This menu choice can create a shortcut to the        upload of the Data Log and place it on the user's desktop.    -   Properties—This menu choice can display the properties dialog        for the Data Log item, as discussed below.

Data Log Shortcuts & Automated Uploads

The user can leverage the Scheduler that comes with Windows to executeautomated uploads of any or all Data Logs. When used with the Clear onUpload feature set in the wizard, this becomes a powerful data gatheringfeature that creates CSV files that can be read by automated programssuch as Excel or Access to track critical items for the user such assales and billing. The user can set the scheduler up to run and canrestart the computer without logging in and the Scheduler canautomatically start and log in the user under the Scheduled account.

To create a scheduled task, the user typically does the following steps:

-   -   1) Create a shortcut to the Data Log to be uploaded at a regular        interval.    -   2) Drag and drop the Data Log shortcut into the Scheduled Tasks        folder found as a subfolder under Control Panel in Windows        Explorer.    -   3) Double click the shortcut and set the times and frequencies        that the upload is to execute.    -   4) Set the login and password for the user account in which the        scheduled task is to run (if the machine is networked).

FIG. 20 shows the result of Step 2.

FIG. 21 illustrates a Windows XP dialog that can allow the user toschedule start and end dates as well as frequency of execution ofscheduled tasks. This is Step 3

FIG. 22 shows a Windows XP dialog that can allow the user to schedulewhen and how often the task (upload of the Data Log) is to be executed.

FIG. 23 shows a Windows XP dialog that can allow the user to configurethe user name and password to run. This is Step 4 and typically is onlynecessary if the user has configured a login account for users on themachine connected to the network.

When the Scheduled Task is properly configured, then the S7-200 explorercan be silently started and the Data Log(s) can be uploaded at theconfigured intervals even if the user is in the process of using themachine already or whether the user had rebooted the machine to runautomatically. The uploaded CSV files can be sent to the following path:C:\Program Files\Siemens\Microsystems\Data Logs\

The CSV files can have the following naming convention:“(PLC_ADDRESS)-USER_DEFINED_DATA_LOG_NAME-DATE-TIME.CSV”

Note that the Colons “:” and slashes “I” can be removed from the dateand time because they typically are not allowed in Windows file names.

The example of FIG. 24 illustrates a Data Log that was configured to runonce an hour from 5:00 April 17 to the end of April 18^(th) every houron the hour. Any of these files can be read by double clicking them orreading them in an automated fashion using Excel, Access or any otherdata base that read CSV files.

Properties Dialog

When the user selects “Properties” from the context menu for a data logitem, the properties dialog of FIG. 25 can be displayed, which can havethe following features:

-   -   The Title of the dialog can be the name of the data log item        plus ‘Properties’    -   The top area of the dialog can repeat the data log item name,        and display the icon used for the data log wizard in STEP        7-Micro/WIN.    -   The size field can display the size of the data log        configuration in the memory cartridge.    -   The Records field can display the number of logged data records        associated with this data log configuration in the memory        cartridge.    -   The Time stamp field can indicate either Yes or No. This can be        an option the user has previously configured in the data log        wizard in STEP 7-Micro/WIN.    -   The Date stamp field can indicate either Yes or No. This can be        an option the user has previously configured in the data log        wizard in STEP 7-Micro/WIN.    -   The Clear on upload field can indicate either Yes or No. This        can be an option the user has previously configured in the data        log wizard in STEP 7-Micro/WIN.    -   The Created field can be the created time for the data log        configuration. This date and time can be formatted in the same        manner as timestamps within the Windows file properties sheet.    -   The Modified field can be the modified time for the data log        configuration. This date and time can be formatted in the same        manner as timestamps within the Windows file properties sheet.

Data Log Shortcut

A Data Log can have a shortcut item created on the desktop. The user canmove this shortcut where as desired and can call the shortcut from aWindows script file, drag it to the Scheduled Tasks folder to run atscheduled intervals, or double click it using explorer. Executing theshortcut (no matter what method used) can attempt to upload the Data Logand output it in a .CSV file in the Data Log folder. Executing from ashortcut can be considered non-interactive and need not show the usererrors but can write the errors to the .CSV file.

Uploading Logged Data

Selecting ‘Upload’ from the context menu, double clicking on a data logitem from within S7-200 Explorer, or double clicking/running a Data Logshortcut can cause the logged data records to be uploaded and convertedto Comma Separated Values (CSV) format. The logged data can be stored inthe C:\Program Files\Siemens\Microsystems\Data Logs folder using thenaming convention of the PLC address inside parenthesis (whether PPIaddress or Ethernet address followed by a hyphen, followed by the userdefined wizard name followed by another hyphen followed by the DATE inthe current culture of Windows set by the current language settingshared by Microwin, followed by a hyphen followed by the TIME in theculture of Windows followed by the .csv (Comma Separated Values)extension. Note that slashes (“1”) and colons (“:”) can be removed andreplaced with hyphens because they cannot be used in Windows file namingconventions.

The user can select to open the file on upload. This action impliesinteractive operation, so this means that it applies only to theright-mouse-click or double-click from within S7-200 Explorer itself NOTfrom any shortcut even if the user double clicks a shortcut. This isbecause S7-200 explorer can detect if the upload operation was startedfrom the shortcut but cannot determine if it was started from anautomation task such as Scheduled Task execution or from a batch file orVB/Java script file.

The user can select to “Open File on Upload” from the right contextmenu. If the item is checked (selecting it toggles the check) and theuser uploads from the S7200 Explorer directly (not from a shortcut),then the namespace explorer can look to see if a CSV file associationexists. If no application is associated with “.csv” then the user can bedisplayed a message showing this fact but the upload executed with theCSV file going to the Data Log folder as described above.

File Items

The Gen 3 memory cartridge item can contain any number of file items,limited only by the space available on the cartridge. Each file itempresent on the MC can be listed individually, in alphabetical order.

-   -   The Icon displayed for file items can be the icon registered for        use with the file's type (extension) with the operating system.        Note that this can vary from user to user.    -   The Name for a file item can be the file name plus its file        extension. Note that these can be always displayed together. The        Windows setting to “hide extensions for known file types” need        not have an affect on this display.    -   The Size for a file item can be the compressed file size. Note        that this can be different than the actual file size.    -   The Modified time for a file item can be the modified time for        the file. Note that this does not represent the time the file        was placed on the memory cartridge.    -   The Created time for a file item can be the creation time for        the file. Note that this does not represent the time the file        was placed on the memory cartridge.

Context Menu

File items can display the following in their context menu:

-   -   Paste—This menu choice typically is only enabled when there is a        file on the Windows® clipboard. This choice writes the file on        the clipboard to the MC. The user can also use the Ctrl+V key        combination when a file item has focus to achieve this        functionality.    -   Delete—Removes the file from the memory cartridge. Since this        can be a destructive action and typically is not undoable, the        user can be asked to confirm this action. The user can also use        the DEL key when a file item has focus to achieve this        functionality.    -   Properties—Displays the properties dialog for the file.

Drag and Drop Support

The namespace can support drag and drop of files with the Gen 3 memorycartridge item. The user can drag files from the Gen 3 memory cartridgeitem and drop them into a directory on their hard drive, or onto thedesktop. Likewise, dropping a file onto the Gen 3 memory cartridge cancause it to be stored in the memory cartridge (if there is spaceavailable). File items can be the only items in the My S7-200 Networknamespace that support drag and drop. The namespace can support the“drag-copy” operation, in which dragging the item makes a copy. Thenamespace need not support “drag-move” in which dragging the itemremoves it from its original location.

File Items with Duplicate Names

When the user attempts to place a duplicate file item on the Gen 3memory cartridge, the operation can overwrite the existing file item.Since this can be a destructive action that typically is not undoable,the user can be asked to confirm the operation. This applied to Pastingitems, and ‘Dropping’ items on the Gen 3 memory cartridge.

Properties Dialog

When the user selects “Properties” from the context menu for a Fileitem, the properties dialog of FIG. 26 can be displayed. This dialog canbe modeled after the File Properties dialog provided with Windows. Thisproperties dialog can have the following features:

-   -   The Title of the dialog can be the name of the file item plus        ‘Properties’    -   The top area of the dialog can repeat the file item name, and        display the icon registered with the operating system for that        type of file (as determined by the file's extension). Note that        this icon can differ between user systems.    -   The Type of file field can display the registered file type for        the file item. This string comes from the registry and can        differ between user systems.    -   The Opens with field can display the application (with icon)        that is registered for the given file type. Again, this comes        from the registry and can differ between user systems.    -   The size field can display the actual file size. Note that this        can differ from the size displayed for the file item in the        memory cartridge.    -   The Compressed size field can display the size of the file item        on the memory cartridge. File items can be compressed to save        space on the memory cartridge. This size can match what is        displayed in the Explorer view for the file item. The percent        shown can be the percent of the original file size that the file        is compressed to. If compression does not save at least one        byte, then the file can be stored uncompressed and compression        size can indicate that the file is not compressed.    -   The Created field can be the created time for the file. This        date and time can be formatted in the same manner as timestamps        within the Windows file properties sheet.    -   The Modified field can be the modified time for the file. This        date and time can be formatted in the same manner as timestamps        within the Windows file properties sheet.

Folder View Options

Windows supports different views for items in a namespace. The My S7-200Network namespace can support the following view options:

-   -   Large Icons—The namespace items can display 32×32 icons. The        label for PLC items can be the network address for the PLC. All        other namespace items can display their name as the label.    -   Small Icons—The namespace items can display 16×16 icons with the        item. The items can display the same label as for the Large        Icons option.    -   List—The namespace items can be displayed in a vertical list.        PLC items can display their 16×16 icon and network address. All        other items can display their 16×16 icon and their name.    -   Details—All the screen captures in this document illustrate the        ‘Details’ view. The section for each type of namespace item        documents the information displayed in the ‘Details’ view.

Sorting

Windows normally provides sorting on each column of information in the‘Details’ view. Sorting can show the files sorted ascending startingwith all “Blocks” followed by all Recipes, followed by all Data Logs,followed by user files. The files can be sub-sorted alphabetically.Clicking on the column headers can cause sorting by that column.Clicking on it again can cause a descending order sort.

Refreshing the Namespace Contents

Refreshing the namespace can cause communications to become active andthe contents of the network to be determined. Note that any time thenamespace is refreshed its contents can change, making the currentlyselected item invalid. When this occurs, the current selection to revertto the namespace item. Refreshing the namespace might also result in anerror. When an error is encountered refreshing the namespace, then allitems can be cleared, an error message displayed (discussed below), andselection can revert to the namespace item.

Some actions within the namespace view can cause additional informationto become visible, but might not necessarily refresh the view. Forinstance, if the user has already refreshed the view (gatheredinformation about all the active devices on the network), they cancontract/expand a tree item (by clicking the “+” or “−” indicatorassociated with the icon) without causing another refresh. This actioncan simply redraw the information, not re-gather it. As a generalstatement, the namespace can follow the standard set by the ‘MyComputer’ namespace with regards to when data is refreshes versus merelyredrawn.

Error Handling

Whenever an error occurs executing a user request, an error dialog canbe displayed with a specific error message and links to possiblesolutions. The title of the error dialog can include the currentcommunications interface. The Close button can always appear on thedialog. The other buttons on the dialog might or might not be visible,depending on the specific error and the user's current communicationssettings. The screen capture of FIG. 27 shows an example of the errordialog with all buttons visible.

-   -   The PG/PC Interface . . . button can be visible when the error        is communications related.    -   The Modem Setup . . . button can be visible when the error is        communications related, and the user has modem communications        selected.    -   The Close button can be visible, possibly at all times.

Possible Error Conditions

Any communications error possible in STEP 7-Micro/WIN can also bepossible from the S7-200 Explorer. The text displayed for these errorscan match those displayed from STEP 7-Micro/WIN.

Some errors specific to Gen 3 memory cartridge operations also can bepossible. See the GPB spec for additional error information possible forGPB operations such as insufficient room for the operation.

A specific error can be possible when the user has created a desktopshortcut to a namespace item (PLC or Gen 3 memory cartridge). When theuser selects the shortcut, this item might no longer be present on thenetwork. In this situation a specific error message can be displayed.

Desktop Shortcuts

Installing the S7-200 Explorer can place a desktop shortcut to the MyS7-200 Network namespace, as discussed earlier. The user also can havethe option to create a desktop shortcut directly to a PLC item, Data Logitem and a Gen 3 Memory Cartridge item. When the user creates a desktopshortcut, the icon used for the shortcut can match the icon of the itemin the namespace. The text for the shortcut can also match the text forthe item in the namespace.

When the user selects one of these desktop shortcuts, the namespace itemthat the shortcut represents can be launched in its own Explorer view.The resulting display can be identical to what would result if the userselected the ‘Open’ context menu choice for the item in the fullnamespace view with the exception of Data Logs where an upload of theData Log occurs but Explorer is not opened.

Whenever a desktop shortcut to a namespace item is launched,communications can be activated to “refresh” the S7-200 network. Thiscan result in an error if either communications cannot be established,or if the item the shortcut represents is no longer present on thenetwork. In either of these situations, an error dialog can result, witha message specific to the error condition. See the error handlingsection for more information.

Note that when the user removes S7-200 Explorer from their machine by anun-installation, only those desktop shortcuts provided by theinstallation are typically removed. Any desktop shortcuts the user hascreated need not be removed. These shortcuts likely will no longerfunction, and the error that results from attempting to launch theshortcut can be determined by Windows.

Multiple Instances of My S7-200 Network

Since the ‘My S7-200 Network’ namespace integrates with WindowsExplorer, any time the user launches an instance of Windows Explorer, aninstance of the namespace can be launched as well. Multiple instances ofMy S7200 Network can exhibit the same communicationsbehavior/limitations as two instances of STEP 7-Micro/WIN and can beaddressed by the out of proc server used by Microsystems programs.

GPB

GPB refers to the “General Purpose Block” which contains memorycartridge directory information in area 1 as well as compressed userfiles in area 3 (if any). S7-200 Explorer uses the IGPB200 interface ifavailable to query contents of the memory cartridge quickly. If notavailable it typically polls the individual blocks and uploads theheaders to determine the sizes. Either way the S7-200 Explorer typicallyoperates identically with or without the presence of a GPB. The designdetails of the GPB and IGPB200 can be found in the document VOB underDocumentCtrl\S7-200\Programming Tools\Engineering Documents\Theories ofOperation\General Purpose Block.doc

Users Guide Browsing the S7-200 Network

The S7-200 Explorer can integrate with Microsoft Windows Explorer toallow browsing of a PPI or Ethernet network. After installing the S7-200Explorer application you can have a new node in your Windows Explorercalled “My S7-200 Network”. If you have STEP 7-Micro/WIN v4.0 loaded onyour computer, you already have the S7-200 Explorer application, nofurther installation is necessary.

Browsing a PPI Network

Double-click on the node “My S7-200 Network” and Windows Explorer canbrowse the PPI network showing a list of attached devices. All possiblenetwork addresses can be polled for attached devices. When a device isfound it can be identified and displayed, as shown in FIG. 28. Thenetwork address assigned to each device is listed in parenthesis.

Tip: If devices are attached or removed from the PPI network use the F5key at any time to refresh the list.

Tip: Not all PLCs and memory cartridges support the functionality of theS7-200 Explorer. Please refer to the S7-200 System Manual for a completelist of hardware features and options.

Browsing an Ethernet Network

Double-click on the node “My S7-200 Network” and Windows Explorer canshow a list of pre-configured IP addresses and the status of theattached device. In an Ethernet network, IP addresses are typicallyconfigured rather than determined automatically. To configure IPaddresses use the IP Address Browser application. You can access thisapplication by using the corresponding right mouse menu item from thenode “My S7-200 Network”, as shown in FIG. 29.

Note: Please refer to the STEP 7-Micro/WIN help system for moreinformation on setting up Industrial Ethernet networks using the S7-200Ethernet and Internet modules.

Communication Settings

The S7-200 Explorer shares the following communication parameters withyour STEP 7-Micro/WIN programming software:

-   -   Access Point (example Micro/WIN->PC/PPI Cable)    -   Local Address    -   Transmission Rate (Baud Rate)    -   Port    -   Other Network Parameters

To change communication settings use the Set PG/PC Interfaceapplication. You can access this application by using the correspondingright mouse menu item from the node “My S7-200 Network”.

Note: Please refer to the STEP 7-Micro/WIN help system for moreinformation on setting up PPI or Industrial Ethernet networks.

Using Modems

If your communication settings can be set to use a modem connection thenyou can establish the modem connection prior to browsing the S7-200network. To establish a connection use the Connect Modem application.You can access this application by using the corresponding right mousemenu item from the node “My S7-200 Network”, as shown in FIG. 30.

After a modem connection is established you can browse the S7-200network. Double-click on the node “My S7-200 Network” and WindowsExplorer can show the list of attached devices. All possible networkaddresses can be polled for attached devices. When a device is found itcan be identified and displayed. The network address assigned to eachdevice is listed in parenthesis.

REMEMBER TO DISCONNECT! When you are finished using the S7-200 Exploreryou must manually disconnect to terminate the modem connection. Closingthe Windows Explorer need not disconnect your modem. To disconnect usethe corresponding right mouse menu item from the node “My S7-200Network”, as shown in FIG. 31.

Browsing the S7-200 PLC

Double-click on any S7-200 PLC to browse the contents of the PLC. ThePLC can contain any of the following:

Program Block (item) Data Block (item) System Block (item) MemoryCartridge (folder)

In the Windows Explorer only folders are typically listed in the Leftpane. A memory cartridge can contain additional items, therefore it canbe a folder. Only the memory cartridge can be listed in the left pane,since it can be the only folder.

Both folders and items can be listed in the Right pane of the WindowsExplorer, as shown in FIG. 32.

Browsing the Memory Cartridge

Double-click on the Memory Cartridge to browse the contents of thecartridge. The Memory Cartridge can contain any of the following:

Program Block (item) Data Block (item) System Block (item) RecipeConfiguration(s) (up to 4 items) Data Log(s) (up to 4 items) UserFile(s) (items)

In the Windows Explorer only folders typically are listed in the Leftpane. There are typically no folders on a memory cartridge, thereforeall of the above items can be listed in the Right pane of the WindowsExplorer, as shown in FIG. 33.

Retrieving Data Log Values

To retrieve Data Log values from the memory cartridge double-click on aData Log node. The data can be uploaded from the memory cartridge andformatted as a .csv file (comma separated values file). The file canthen be opened by the application you have associated with .csv fileextensions. Typically this application can be Microsoft Excel.

Note: You must have an application associated with .csv file extensionsbefore the Data Log values can be uploaded.

Note: If you set the wizard option to clear the Data Log values onUpload, you must make sure you save the data. Use the associatedapplication, Microsoft Excel, and save your data to a directory andfilename you are familiar with.

The screen shot shown in FIG. 34 is an example of Data Log valuesuploaded into Excel. After double-clicking on the Data Log node from theWindows Explorer the values can be uploaded and opened in Excel.

Tip: It is recommended that you immediately perform a Save As functionto save the data to a directory and filename that you are familiar with.

Adding User Files

You can use the free space of a memory cartridge to store your STEP7-Micro/WIN project file or any other files you wish. The files can becompressed as they are dragged and dropped onto the memory cartridgenode by the S7-200 Explorer. You do not have to use a separatecompression utility such as WinZip. If a file is already compressed asecond compression typically is not performed. You can view theproperties of any file you put on the memory cartridge by using theright mouse menu item “Properties”.

To add a file to the memory cartridge simply drag and drop the file ontothe memory cartridge folder. You can also use the right mouse menu itemscopy and paste.

Memory Cartridge Properties

The right mouse menu item Properties displays the screen shown in FIG.35. You can use this screen to quickly summarize the used and free spaceavailable on the memory cartridge.

Clearing the Memory Cartridge

The right mouse menu item Clear, on a Memory Cartridge node, can allowyou to erase all items.

Still other embodiments will become readily apparent to those skilled inthis art from reading the above-recited detailed description anddrawings of certain exemplary embodiments. It should be understood thatnumerous variations, modifications, and additional embodiments arepossible, and accordingly, all such variations, modifications, andembodiments are to be regarded as being within the spirit and scope ofthis application. For example, regardless of the content of any portion(e.g., title, field, background, summary, abstract, drawing figure,etc.) of this application, unless clearly specified to the contrary,such as via an explicit definition, there is no requirement for theinclusion in any claim herein or of any application claiming priorityhereto of any particular described or illustrated activity or element,any particular sequence of such activities, or any particularinterrelationship of such elements. Moreover, any activity can berepeated, any activity can be performed by multiple entities, and/or anyelement can be duplicated. Further, any activity or element can beexcluded, the sequence of activities can vary, and/or theinterrelationship of elements can vary. Accordingly, the descriptionsand drawings are to be regarded as illustrative in nature, and not asrestrictive. Moreover, when any number or range is described herein,unless clearly stated otherwise, that number or range is approximate.When any range is described herein, unless clearly stated otherwise,that range includes all values therein and all subranges therein. Anyinformation in any material (e.g., a United States patent, United Statespatent application, book, article, etc.) that has been incorporated byreference herein, is only incorporated by reference to the extent thatno conflict exists between such information and the other statements anddrawings set forth herein. In the event of such conflict, including aconflict that would render invalid any claim herein or seeking priorityhereto, then any such conflicting information in such incorporated byreference material is specifically not incorporated by reference herein.

What is claimed is:
 1. A non-PLC (programmable logic controller)information device, comprising: a processor; a memory coupled to theprocessor; and a PLC network interface coupled to the processor and tothe memory, the PLC network interface configured to: connect to a PLCnetwork; present the PLC network as a namespace shell extension of anoperating system of the non-PLC information device; render the PLCnetwork as a node of a network to which the non-PLC information deviceis connected, and initiate a search within any one or more of the PLCnetwork, a PLC coupled to the PLC network, and a PLC memory devicecoupled to the PLC in response to a user entering one or more searchparameter values via the non-PLC information device.
 2. The informationdevice of claim 1, wherein the PLC network interface is configured topoll for PLC networks and devices coupled thereto and to identifyrespective addresses thereof that are coupled to the non-PLC informationdevice.
 3. The information device of claim 1, wherein the PLC networkinterface is configured to provide browsing access of the PLC network,the PLC, and the PLC memory device.
 4. The information device of claim1, wherein the PLC network interface is configured to provideinformation transfer capability between the non-PLC information deviceand the PLC network, the PLC, and the PLC memory device.
 5. Theinformation device of claim 4, wherein the PLC network interface isconfigured to render a transfer of information between the non-PLCinformation device and the PLC network, the PLC, or the PLC memorydevice as an icon or animation.
 6. The information device of claim 1,wherein the PLC network interface is configured to render the PLCnetwork, the PLC, or the PLC memory device as a volume, directory,folder, or predetermined icon.
 7. The information device of claim 1,wherein the PLC network interface is configured to render the PLCnetwork, the PLC, or the PLC memory device as a hierarchical structureor path.
 8. The information device of claim 1, further comprising theoperating system of the non-PLC information device, wherein theoperating system is a personal computer operating system.
 9. Theinformation device of claim 1, wherein the PLC network interface isconfigured to receive from a user one or more search parameter valuesfor searching files including content and metadata thereof within one ormore of the PLC network, the PLC, and the PLC memory device, the searchparameter values including an address of an item, any portion of an itemname, an item type, item creation information, item size, a textualcontent of an item, a graphical content of an item, an image content ofan item, an audio content of an item, a video content of an item, and ananimation content of an item.
 10. A system, comprising: a first PLC(programmable logic controller) network; a first PLC coupled to thefirst PLC network; a first PLC memory device coupled to the first PLC;and a non-PLC information device coupled to the first PLC network, thenon-PLC information device comprising: a processor; a memory coupled tothe processor; and a PLC network interface coupled to the processor andto the memory, the PLC network interface configured to: poll for andidentify respective addresses of PLC networks and devices coupledthereto that are coupled to the non-PLC information device; present thefirst PLC network as a namespace shell extension of an operating systemof the non-PLC information device; and initiate a search within any oneor more of the first PLC network, the first PLC, and the first PLCmemory device in response to a user entering one or more searchparameter values.
 11. The system of claim 10, wherein the PLC networkinterface is configured to render identified PLC networks as respectivefolders containing an item for each identified device coupled thereto.12. The system of claim 10, wherein the PLC network interface isconfigured to render a program or file stored in the first PLC memorydevice as a folder item.
 13. The system of claim 10, further comprising:a second PLC network; a second PLC coupled to the second PLC network;and a second PLC memory device coupled to the second PLC; wherein: thenon-PLC information device is coupled to the second PLC network, and thePLC network interface is configured to: poll for and identify respectiveaddresses of the second PLC network, the second PLC, and the second PLCmemory device; present the second PLC network as a namespace shellextension of the operating system of the non-PLC information device; andinitiate a search within any one or more of the first PLC network, thefirst PLC, the first PLC memory device, the second PLC network, thesecond PLC, and the second PLC memory device in response to a userentering one or more search parameter values.
 14. The system of claim13, wherein the PLC network interface is configured to render the firstPLC network as a first node and the second PLC network as a second nodeof a network to which the non-PLC information device is connected. 15.The system of claim 13, wherein the PLC network interface is configuredto provide information transfer capability between: the non-PLCinformation device and the first PLC network, the first PLC, and thefirst PLC memory device; and the non-PLC information device and thesecond PLC network, the second PLC, and the second PLC memory device.16. A method of accessing information within a PLC (programmable logiccontroller) network, comprising: providing a non-PLC information devicecomprising a processor, a memory coupled to the processor, and a PLCnetwork interface coupled to the processor and the memory, the PLCnetwork interface configured to connect to a PLC network and to presentthe PLC network as a namespace shell extension of an operating system ofthe non-PLC information device; rendering via the PLC network interfacethe PLC network as a node of a network to which the non-PLC informationdevice is connected, and initiating a search via the PLC networkinterface within any one or more of the PLC network, a PLC coupled tothe PLC network, and a PLC memory device coupled to the PLC in responseto a user entering one or more search parameter values.
 17. The methodof claim 16, further comprising polling for and identifying respectiveaddresses of, via the PLC network interface, one or more PLC networksand devices coupled thereto that are coupled to the non-PLC informationdevice.
 18. The method of claim 16, further comprising rendering via thePLC network interface the PLC network, the PLC, or the PLC memory deviceas a volume, directory, folder, or predetermined icon.
 19. The method ofclaim 16, further comprising providing browsing access via the PLCnetwork interface of the PLC network, the PLC, or the PLC memory device.20. The method of claim 16, further comprising providing informationtransfer capability via the PLC network interface between the non-PLCinformation device and the PLC network, the PLC, and the PLC memorydevice.